Ignore HTTP 451 errors "Repository access blocked" when retrieving metadata#282
Open
olbat wants to merge 1 commit intojekyll:mainfrom
Open
Ignore HTTP 451 errors "Repository access blocked" when retrieving metadata#282olbat wants to merge 1 commit intojekyll:mainfrom
olbat wants to merge 1 commit intojekyll:mainfrom
Conversation
…tadata GitHub returns 451 errors when trying to access any repository & forks that has been taken down for legal reason (e.g. DMCA Takedown). Repositories in this situation are being frozen. Its not possible to access to their settings anymore and therefore not possible to delete them. Even through GitHub REST API. The only option to delete them is to open a ticket for GitHub support, which is likely to never be touched, for free accounts. In case any one of your repositories or forks gets taken down for such reason, using the _jekyll-github-metadata_ plugin becomes impossible as the HTTP client fails as follow: ``` Liquid Exception: GET https://api.github.com/repos/USER/REPO/releases?per_page=100: 451 - Repository access blocked in _pages/page.md rake aborted! Octokit::UnavailableForLegalReasons: GET https://api.github.com/repos/USER/REPO/releases?per_page=100: 451 - Repository access blocked (Octokit::UnavailableForLegalReasons) ``` This change unblocks accounts in this situation and makes the `Octokit::UnavailableForLegalReasons` exception being ignored if it's encountered while retrieving repositories' metadata.
olbat
changed the title
|
this is important and need to be merged, i facing this problem too |
|
Other people are also facing the same problem, ref mzlogin/mzlogin.github.io#193 Please help resolve it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub returns 451 errors when trying to access any repository & forks that has been taken down for legal reason (e.g. DMCA Takedown).
Repositories in this situation are being frozen. Its not possible to access to their settings anymore and therefore not possible to delete them. Even through GitHub REST API. The only option to delete them is to open a ticket for GitHub support, which is likely to never be touched, for free accounts.
In case any one of your repositories or forks gets taken down for such reason, using the jekyll-github-metadata plugin becomes impossible as the HTTP client fails as follow:
This change unblocks accounts in this situation and makes the
Octokit::UnavailableForLegalReasonsexception being ignored if it's encountered while retrieving repositories' metadata.